Skip to content

[Fleet] Update "Remote Elasticsearch output” #2048

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
Jul 25, 2025

Conversation

vishaangelova
Copy link
Contributor

@vishaangelova vishaangelova commented Jul 5, 2025

This PR is a review/update of the documentation created for [Fleet] Multi Cluster Fleet support - Phase 1: Global Visibility and Control, Local Data Plane, and updates the Remote Elasticsearch output doc with the following:

  • Updated the doc frontmatter to include applies_to
  • Moved the “Automatic integrations synchronization” section to a new doc below “Remote ES output"
  • Removed references to specific subscriptions, added a reworded note in the “Automatic integrations synchronization” section doc
  • Clarified the remote address required for setting up a remote cluster
  • Added links to deploy-manage guides for setting up remote clusters and cross-cluster replication in the relevant sections
  • Restructured and updated the steps in the document for clarity and a more logical workflow
  • Added info about the available remote cluster data views in a new section
  • Added a new troubleshooting section

Closes elastic/ingest-docs#1817

Preview

reference/fleet/automatic-integrations-synchronization.md
reference/fleet/remote-elasticsearch-output.md

@vishaangelova vishaangelova requested a review from a team as a code owner July 5, 2025 14:09
Copy link

github-actions bot commented Jul 5, 2025

@vishaangelova vishaangelova force-pushed the 1817-cross-cluster-integration-updates branch from 2a6364e to 564d582 Compare July 5, 2025 14:50
@vishaangelova vishaangelova marked this pull request as draft July 5, 2025 19:06
@vishaangelova vishaangelova force-pushed the 1817-cross-cluster-integration-updates branch from 564d582 to a88458e Compare July 5, 2025 20:21
@vishaangelova vishaangelova force-pushed the 1817-cross-cluster-integration-updates branch from a88458e to a21b40e Compare July 5, 2025 21:47
@vishaangelova vishaangelova marked this pull request as ready for review July 5, 2025 21:54
Copy link
Member

@bmorelli25 bmorelli25 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great improvements. A few comments.

@vishaangelova vishaangelova marked this pull request as draft July 22, 2025 16:38
@vishaangelova vishaangelova marked this pull request as ready for review July 23, 2025 09:13
Copy link
Contributor

@juliaElastic juliaElastic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@bmorelli25 bmorelli25 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work 👍

@vishaangelova vishaangelova merged commit eed1df4 into main Jul 25, 2025
8 checks passed
@vishaangelova vishaangelova deleted the 1817-cross-cluster-integration-updates branch July 25, 2025 07:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[REQUEST]: Document Multi Cluster Fleet support - Phase 1
4 participants